-
Notifications
You must be signed in to change notification settings - Fork 23
Only create one PR when updating dependencies #1938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
seunghun1ee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea on using pr_body.md when creating PR.
|
recheck |
a635de2 to
4834ac8
Compare
Co-authored-by: Eric Le Lay <eric@stackhpc.com>
priteau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Alex-Welsh, let's try it!
Usually every Tuesday, I have to go through all the open dependency bump PRs and merge the changes that target the same branch. This saves CI resources and PR spam.
This PR automates that process, so only one PR will be created per branch, with one commit for each dependency that gets bumped.
Some changes made with Gemini. I've manually checked everything though.
Also includes a few minor tweaks like changing the name of input var and moving to an Ubuntu Noble runner
Tested & working:
[1] #1937
[2] #1936